Previously, Portico did not allow secondary transactions (e.g., CreditTxnEdit, CreditIncrementalAuth) to be made from a different SiteId or DeviceId from where the original purchase was run. Cross-Site or Cross-Device processing allows merchants to send secondary transactions from a different SiteId and/or DeviceId from where the original purchase was made. For example, If a merchant is set up for Cross-Device processing, a tip adjust can be submitted from a different device than from where the sale was made as long as both devices are associated with the same SiteId. If a merchant is set up for Cross-Site processing, then a secondary transaction can be submitted from a different SiteId or DeviceId from where the original purchase was made. An example of Cross-Site processing is when a customer makes a purchase from a merchant’s eCommerce Site and then the customer returns the purchase at the brick-and-mortar store, where each entity has a unique MID.

Generally, secondary transactions affect the original authorization or purchase and thus their processing is conducted on the same DeviceId associated with that original transaction. Transaction processing, reporting, and settlement on the device of the original authorization will reflect any Cross-Site or Cross-Device secondary transaction processing associated with that original authorization. This means that batches associated with the original transaction’s device will reflect the Cross-Site or Cross-Device secondary transaction processing and not the batches of the DeviceId from where the secondary transaction was run. This is true except for Return processing where the Return is processed on the same SiteId and DeviceId where the cardholder returned their purchase. The batch where the Return was made is adjusted versus the one where the original purchase was made.

Cross-Site and Cross-Device processing is supported with the following services:

• AddAttachment
• BatchClose (Cross-Device only)
• CheckVoid
• CreditAdditionalAuth
• CreditAddToBatch
• CreditCPCEdit
• CreditIncrementalAuth
• CreditReturn
• CreditReversal
• CreditTxnEdit
• CreditVoid
• DebitReturn
• DebitReversal (Cross-Site or Device processing is not supported for Canadian Interac Debit transactions)
• EBTFSReturn
• EBTFSReversal
• FindTransactions
• GetAttachments
• GetTransactionStatus
• GiftCardReversal
• GiftCardVoid
• ReportBatchSummary
• ReportTxnDetail

Cross-Site and Cross-Device processing is supported with the Exchange, GSAP-NA, and GSAP-AP Authorization Platforms.

Merchants wanting to take advantage of this functionality must be enabled for it.